Selecting and sending subset of components to computing device prior to operating system install

ABSTRACT

Examples disclosed herein relate to providing a subset of software components customized for a device to the device prior to the device installing an associated operating system. An update platform including a repository including a number of software components associated with multiple operating systems and multiple hardware sets is to determine that an operating system install is to occur on the device. The update platform is to select a subset of the software components for the device based on the operating system install and hardware devices on the device. The update platform is to push the subset to a storage coupled to a baseboard management controller of the device prior to the operating system install.

CROSS REFERENCE TO RELATED APPLICATION

This is a continuation of U.S. application Ser. No. 16/392,310, filedApr. 23, 2019, U.S. Pat. No. 11,334,337.

BACKGROUND

Computing systems utilize various software components. For example, lowlevel firmware to interface with the hardware and drivers for hardwarethat may interface with an operating system. In some cases, it may benecessary to update the firmware or drivers on a computing system. Forexample, updates may provide additional capabilities. As anotherexample, updates may correct errors, often referred to as bugs, inprevious versions of the firmware or drivers.

BRIEF DESCRIPTION OF THE DRAWINGS

The following detailed description references the drawings, wherein:

FIG. 1 is a block diagram of a system including an update platform thatis capable to provide customized component install set for an operatingsystem to a baseboard management controller of a computing device priorto installation of the operating system, according to an example;

FIG. 2 is a block diagram of an update platform capable to determine andsend a subset of software components customized for an operating systemto a baseboard management controller of a computing device prior toinstallation of the operating system, according to an example;

FIG. 3 is a flowchart of a method for sending a subset of softwarecomponents customized for an operating system to a baseboard managementcontroller of a computing device prior to installation of the operatingsystem, according to an example;

FIG. 4 is a block diagram of a computing device with a baseboardmanagement controller capable of storing software components to installcustomized for an operating system prior to installation of thatoperating system; and

FIG. 5 is a flowchart of a method for receiving a customized softwarecomponent subset at a baseboard management controller of a computingdevice customized for an operating system not yet installed on thecomputing device.

Throughout the drawings, identical reference numbers may designatesimilar, but not necessarily identical, elements. An index number “N”appended to some of the reference numerals may be understood to merelydenote plurality and may not necessarily represent the same quantity foreach reference numeral having such an index number “N”. Additionally,use herein of a reference numeral without an index number, where suchreference numeral is referred to elsewhere with an index number, may bea general reference to the corresponding plural elements, collectivelyor individually. In another example, an index number of “I,” “M,” etc.can be used in place of index number N.

DETAILED DESCRIPTION

Computing devices, such as servers, in a datacenter or other locationmay have one or multiple operating systems installed. Installing orupdating an operating system (OS) may involve logging into an OS of acomputing system, using an account credential that grants administratorprivileges. The administrator, often referred to as the root user, orsuperuser, is granted privileges on the computer system that may exceedthose that are available to a general user account. For example,execution of certain programs on the system may be limited to users thathave administrator privileges. Included in those privileges may be theauthority to perform updates on the firmware and/or drivers or to makeconfiguration changes on the computer system. For purposes of thisdescription, administrator credentials or operating system administratorcredentials, refers to the credentials needed to log into a computersystem as an administrator, and thus be granted administratorprivileges.

A user logged in as an administrator may then download any software usedin updating the firmware and/or drivers. This downloaded data may bereferred to as an update package, as it may include the data used toperform the firmware and/or driver update. This data may include anexecutable program that actually performs the update. The update packagemay be downloaded to the server computer over a network. Theadministrator user may then update the desired components or performconfiguration updates on the computer. For the remainder of thisdisclosure, the term update or updating refers to updating of firmwareand/or drivers, as well as altering the configuration of a servercomputer.

Several issues may arise when using the process described above. Oneissue that arises is that often times the updating of the system mayinterfere with normal operation of the system. For example, performingan update may reduce the responsiveness of the system. In some cases,the update process may require that the system be restarted. Theseoperations may impact the workloads that are being processed by theserver. For example, in the cases where the server is restarted, thatserver is no longer available during the restart period.

As used herein, a “live server” is a computing system providing aservice where the service is being provided. As used herein, a“maintenance window” is the time that a live server is taken down toperform maintenance activity (e.g., an upgrade of an OS, upgrade of adrivers, upgrade of firmware on a system, etc.).

When installing an OS, the OS upgrade package may not have an image ofdrivers customized for a particular type of machine (e.g., theprocessor, the bus adapter cards, etc.). A separate “software componentpackage” may be separately downloaded to the computing device to beupgraded. However, as noted, the traditional approach is to update theOS and then download the drivers needed for that particular OS. This canlead to additional downtime and be implemented at a second maintenancewindow. Further, in some examples, a production network used to provideservices that may be used for downloading the OS upgrade package and/orthe “software component package.” This can be the same network that isused to provide services by a live server. As such, downloading via thisnetwork can take some of the bandwidth that the server uses to processserver workload. Moreover, the size of every permutation of eachcomputing device hardware set and supported operating systems can belarge. Accordingly, a customized subset of a larger supported softwarecomponent set may be desirable.

Various embodiments described herein relate to a mechanism where anupdate platform can provide a software component package customized fora computing device to that computing device via management network usinga baseboard management controller of the computing device. The softwarecomponent package can be sent prior to installation of a new operatingsystem and even before the new operating system is provided to thecomputing device.

An operating system management platform can be used to manage operatingsystems on a number of computing devices including the computing deviceto install a new OS on. The OS management platform can determine that anew OS should be installed on a particular computing device. This can bebased on a user input, based on a predetermined plan or schedule, or bebased on a workload management algorithm. Using a workload managementalgorithm can be useful, for example, when there are changes in usage ofthe datacenter that the computing devices are contained within.

The OS management platform can send information to an update platformthat has access to a management network that baseboard managementcontrollers (BMCs) associated with the computing devices have access to.The update platform can learn from the OS management platform that thenew OS install is scheduled or is going to be scheduled. The OSmanagement platform can provide details about the OS. The details mayinclude, for example, a name and/or version number of the OS and theselected computing device.

The update platform can learn from the computing device what hardwarecomponents are present on the computing device via the managementnetwork and BMC. The update platform can then select software componentsfor the computing device based on the OS to be installed and thehardware present on the particular computing device. In some examples,the hardware components can be determined after the determination thatthe OS is going to be installed and in response to the determination toinstall the OS. In other examples, the hardware components can bedetermined by the update platform querying the BMC of the particularcomputing device prior to the determination to install the OS.

The update platform can include a repository that includes a collectionof software components that may be used with the computing devices andOSes. In some examples, the update platform can include a data structurethat associates each component to one or multiple hardware device and/orone or multiple OSes. The update platform can take the informationreceived about the OS that is to be installed on the computing deviceand filter the software components to a subset of the softwarecomponents that are associated with the OS. The update platform can alsofilter the software components based on the hardware components presenton the computing device. Similarly, the update platform can filter basedon both to determine a subset of the software components applicable toboth the OS to be installed and the computing device.

The subset of software components can then be sent to the BMC of thecomputing device. In one example, the update platform can push thesubset of software components to the BMC. The BMC can store the subsetof software components in a local repository. That storage can be, forexample, on a flash storage incorporated within the BMC or accessiblevia a bus. The local repository may also be accessible to an operatingsystem once the operating system is installed. After the softwarecomponent subset has been transferred to the repository, the OS can besent and installed. Various approaches can be used for the OS install.For example, the OS management platform may cause download through aproduction network and install an OS install package, the OS installpackage may be downloaded to the computing device via the BMC as withthe software component subset, etc.

The OS install package can be executed to install the OS image on thecomputing device. The OS can be restarted, if necessary to completeinstallation. Further, after the installation is complete, the subset ofthe software components can be installed, In one example, the repositorythat the subset of software components resides can be exposed by the BMCto the OS. The OS, thus has access to the subset of software components.In one example, a script can be executed to install the softwarecomponents. The script can be part of the subset of software components.

In some examples, the OS image that is installed can be pre-configuredto be able to access the repository, for example, using a known driverfor the ecosystem. In some examples, one or more of the softwarecomponents are executable to install themselves. In other examples,scripts or other software can be executed by the OS to install one ormore of the software components. Examples of software components caninclude drivers. In some examples, firmware can also be included in thesoftware components. In some examples, the BMC or other firmwareexecutable on the computing device can install the update. Because thesoftware component subset is already present, there is no need toseparately download the software components. Further, because theapplicable subset is already determined for the new OS before the new OSis even installed, bandwidth is not taken to send all of the collectionof components to the computing device.

As used herein, an “operating system install” is a determination toinstall a new or upgraded operating system onto a computing device. Asused herein, an “operating system install package” is a file or set offiles that can be used to install an operating system onto a computingdevice. An operating system install can occur on a computing device thatalready has an OS present or can occur on a computing device without aninstalled high level operating system.

As used herein, a “software component” is a set of instructions, code,etc. that can be installed to be executed by a processor on a computingdevice. Examples of software components include firmware that can beexecuted by microcontrollers or a central processing unit, drivers tocommunicate between an operating system and hardware of a computingdevice, and other software that can execute such as middleware,management software, etc. As used herein, an “Operating System” is a setof software of a computing device that manages computer hardware andsoftware resources and provides common services for computer programssuch as scheduling tasks, executing applications, controllingperipherals, etc. Examples of OSes include LINUX, WINDOWS, hypervisors,etc. A hypervisor or virtual machine monitor is computer software,firmware and/or hardware that creates and runs virtual machines. Ahypervisor can present a virtual operating platform to guest virtualmachines.

FIG. 1 is a block diagram of a system including an update platform thatis capable to provide customized component install set for an operatingsystem to a baseboard management controller of a computing device priorto installation of the operating system, according to an example. Thesystem 100 can include an update platform 102 that communicates withcomputing devices 108 a-108 n via a management network 109. The updateplatform 102 can have access to a collection of components 120.Moreover, the update platform can be communicatively coupled to an OSmanagement platform 106. In certain examples, the update platform 102,OS management platform 106, computing devices 108 can be implementedusing one or more of computing devices, such as servers, clientcomputers, desktop computers, mobile computers, etc. The computingdevices can be implemented via a processing element, memory, and/orother components. In some examples, platforms may be run in one or morevirtual machines executing on a computing device.

As noted above, a user or administrator of a datacenter may wish toinstall or update operating systems on one or more computing devices 108a-108 n. While doing this, a set of software components may be used toon the respective computing device 108. The update platform 102 can haveaccess to a collection of components 120. In some examples, thecollection of components 120 is stored as part of the update platform102, on the same computing device, or is accessible via a storage to theupdate platform 102.

The collection of components 120 can include, firmware and/or settingsfor one or more hardware components present on the computing devices.Further, the collection of components 120 can include drivers that canbe installed on an operating system installed on the devices. In someexamples, other software, such as middleware to can be included in thecollection of components 120. The collection of components 120 caninclude a superset of supported software components for multiple of thecomputing devices. This can be, for example, a package of componentsthat would be included in a service pack from a manufacturer of thecomputing devices. As such, multiple hardware sets can be supported. Asused herein, a “hardware set” includes physical hardware (e.g.,peripheral devices, microcontrollers, processors, memory, etc.) that maybe included on a device. In some examples, a supported hardware set is aset for which a software component is available to be installed via thecollection of components 120. Further, some components can be specificfor particular operating systems (e.g., drivers for operating aparticular hardware component for a particular OS). Hardware devices mayinclude input output devices, peripheral devices connected via a bussuch has a peripheral component interconnect (PCI), controllers tocontrol busses, specific purpose hardware, etc. Multiple operatingsystems can include different versions of a same operating system type,operating systems of similar manufacturers, but with differentconfigurations, operating systems from different manufacturers, or thelike. As noted above, the OS may be a hypervisor.

In some examples, each software component can be associated withinformation regarding the particular software components relevance to aparticular operating system and/or hardware component. The informationcan be in the form of information in a table or linked list, one ormultiple tags, metadata, other data structure used to keep theinformation, etc. The collection of components 120 can be a large amountof information and it could take up much bandwidth on the managementnetwork 109 or other network to transfer the entire collection to eachcomputing device 108.

Each computing device 108 can include a BMC 110 a-110 n. In someexamples, the BMC 110 can be used to implement services for thecomputing device 108. BMC 110 can be implemented using a separateprocessor from the processor 114 a-114 n that is used to execute a highlevel operating system (e.g., OS 116 a-116 n). BMCs can provideso-called “lights-out” functionality for computing devices. The lightsout functionality may allow a user, such as a systems administrator, toperform management operations on the computing device 108 even if anoperating system is not installed or not functional on the computingdevice.

Moreover, in one example, the BMC 110 can run on auxiliary power, thusthe computing device 108 need not be powered on to an on state wherecontrol of the computing device 108 is handed over to an operatingsystem after boot. As examples, the BMC 110 may provide so-called“out-of-band” services, such as remote console access, remote reboot andpower management functionality, monitoring health of the system, accessto system logs, and the like. As used herein, a BMC 110 has managementcapabilities for sub-systems of a computing device 108, and is separatefrom a processor or processing element that executes a main operatingsystem of a computing device (e.g., a server or set of servers).

The BMC 110 may comprise an interface, such as a network interface,and/or serial interface that an administrator can use to remotelycommunicate with the BMC 110. As used herein, an “out-of-band” serviceis a service provided by the BMC 110 via a dedicated management channel(e.g., the network interface or serial interface) and is availablewhether the computing device 108 is in powered on state. In someexamples, a BMC 110 may be included as part of an enclosure. In otherexamples, a BMC 110 may be included in one or more of the servers (e.g.,as part of the management subsystem of the server) or connected via aninterface (e.g., a peripheral interface). In some examples, sensorsassociated with the BMC 110 can measure internal physical variables suchas humidity, temperature, power supply voltage, communicationsparameters, fan speeds, operating system functions, or the like. The BMC110 may also be capable to reboot or power cycle the device. As noted,the BMC 110 allows for remote management of the device, as such,notifications can be made to a centralized station such as the updateplatform 102 or a management platform using the BMC 110 and passwords orother user entry can be implemented via the BMC 110.

The BMC 110 a-110 n can have a storage 112 a-112 n coupled to the BMC110 a-110 n. The storage 112 can be, for example, on a flash storageincorporated within the BMC 110 or accessible via a bus. The storage 112can act as a local repository that may also be accessible to anoperating system once the operating system is installed.

Further, the computing device may include a plurality of hardwaredevices or components. Examples, of hardware components includecontrollers, add on cards, peripherals, field programmable gate arrays(FPGAs), complex programmable logic devices (CPLDs), applicationspecific integrated circuits (ASICs), system on chips, etc. In someexamples, one or more of the hardware components can be inventoried orcommunicatively coupled to the BMC 110, either directly or viaintermediary components. For example, the BMC 110 may request thatanother firmware (e.g., a basic input output system) take an inventoryof one or more components if the BMC 110 is incapable of directcommunications. The BMC 110 can provide the hardware devices that arepresent on a particular computing device 108 to the update platform 102.This can occur on request, periodically, etc.

The OS management platform 106 can determine to cause installation of anoperating system on a computing device 108. The OS management platform106 can make the determination various ways, one example way is todetermine that a system with a particular OS is needed to provide aparticular service based on a load balancing algorithm for thedatacenter. Another example is a user configuration. A further exampleis based on a request. The OS management platform 106 can determine howthe OS management platform 106 wants the computing device 108 to beconfigured and create a request for the update platform 102.

The update platform 102 is to expose an application programminginterface (API) to the OS management platform 106. In some examples, theOS management platform 106 can be implemented as a virtual machinemanagement system. In some examples, the API can be configured to workwith more than one OS management platform can be management systemagnostic. The request can include an identification to use thecollection of components 120, which operating system to install, etc.The request can also identify the particular computing device 108. Therequest can be consider information associated with an operating systeminstall.

In response to receiving the request, the update platform 102 determinesthat an operating system install is to occur on the computing device108. The update platform 102 can take the information and determine aset of the supported OS, drivers, and firmware. In one example, theupdate platform 102 uses the information to select a subset of thecollection of components 120 that are relevant for the identified OS. Inone example, the potential components can be filtered by the identifiedOS. Further, as noted above, the BMC 110 can provide hardware deviceinformation about the hardware devices present on the identifiedcomputing device 108. The collection of components 120 can further befiltered based on hardware devices present to create a subset of thecollection of components.

The subset can then be sent to the BMC 110 to be stored on its storage112. In one example, the update platform 102 can push the subset down tothe BMC 110. The subset can be in the form of a package or individualfiles. The package and/or individual files can be self-executable orexecuted via a different method. In some examples, the update platform102 can push the subset to the storage 112 prior to the operating systemto be installed is installed using an operating system install package.The update platform 102 can push the subset to the storage 112 while thecomputing device is acting as a live server. The live server can beimplemented using an old operating system prior to install of the newOS. In another example, the server may not be executing an operatingsystem. The pushing of the subset to the BMC 110 can be consideredstaging.

The operating system install package can also be sent to the computingdevice 108. In one example, the update platform 102 or a managementplatform sends the operating system install package to the computingdevice via the BMC 110. In another example, the operating system installpackage can be sent via other means, for example, via a productionnetwork or a secondary management network that the OS managementplatform 106 can directly communicate with one or more of the computingdevices 108 with. In some examples, the computing device 108 receivesthe subset of components before receiving the OS install package.

The processor 114 can execute instruction to install the operatingsystem install package. In some examples, the OS can access the storage112 after being installed. In some examples, the OS is installed with adriver or other software that is capable of accessing the storage 112.Implementation can be performed using an infrastructure automation toolsuch as Chef. Chef is a tool designed for automation at scale usingRuby. In some examples, the OS can be configured to install the subseton the storage 112. The install could be as part of a periodic routineto check if anything new is on the storage and, if so, check credentialsand install if appropriate. The install could also be as part of aninstall procedure for the OS. In some examples, for a live server, theinstall of the operating system and the subset can be within a singlemaintenance window.

In some examples, all of the subset is not installed. This can happen,for example, if the associated driver or firmware has more than onecomponent. In some examples, the BMC 110 can install or cause updatesfor firmware for hardware devices separate from the installation ofdrivers via the OS. In some examples, some of the associated softwarecomponents are installed via the OS (e.g., middleware, drivers, etc.).As noted, these can be selected for the particular OS installed as wellas the particular hardware devices identified by the BMC 110 to be onthe computing device.

The management network 109 can be a communication network that can usewired communications, wireless communications, or combinations thereof.Further, the communication network can include multiple subcommunication networks such as data networks, wireless networks,telephony networks, etc. Such networks can include, for example, apublic data network such as the Internet, local area networks (LANs),wide area networks (WANs), metropolitan area networks (MANS), cablenetworks, fiber optic networks, combinations thereof, or the like. Incertain examples, wireless networks may include cellular networks,satellite communications, wireless LANs, etc. Further, the communicationnetwork can be in the form of a direct network link between devices.Various communications structures and infrastructure can be utilized toimplement the communication network(s).

By way of example, computing devices communicate with each other andother components with access to the communication network via acommunication protocol or multiple protocols. A protocol can be a set ofrules that defines how nodes of the communication network interact withother nodes. Further, communications between network nodes can beimplemented by exchanging discrete packets of data or sending messages.Packets can include header information associated with a protocol (e.g.,information on the location of the network node(s) to contact) as wellas payload information.

In some examples, the BMCs 110 can communicate with each other and/orthe update platform 102 via the management network 109. In theseexamples, the BMCs 110 can be coupled to network interface cards (NICs)that can connect to the management network 109.

For various purposes, for example, security, the management network 109can be isolated from a production network that the OSes 116 installed onthe computing devices 108 provide services through and/or can beaccessed directly through. The production network can use a separatecommunication network. In some examples, isolation can be implementedvia virtual networks. In other examples, isolation can be implementedvia using separate hardware (e.g., network switches).

In one example, the OS management platform can perform a precheck on theOS and software component set to be installed. As noted, the OSmanagement platform 106 can create a request for a particular OS to beinstalled on an identified computing device to the update platform 102.The update platform 102 can read the metadata for the collection ofcomponents 120 can determine a supported OS, associated drivers, andassociated firmware. The set can be identified via an identifier. Theidentifier can be used to identify a premade or predetermined subsetpackage that can be used. The information can be sent back to the OSmanagement platform 106.

The OS management platform 106 can then request that the update platformcall the particular subset package using the identifier to set this asthe package to be used with the particular computing device to installthe new OS on. A precheck can then be called by the OS managementplatform 106 for the identifier. In one example, during the precheckstage, the update platform 102 reads a firmware inventory from a BMC 110associated with the computing device 110. In some examples, if there isa current OS 116 on the computing device 110, some of the information isreceived via an agent on the OS 116.

Then, the update platform 102 identifies and/or creates the install set.The update is then staged by pushing the install set to the storage 112via the BMC 110. Once the new OS is updated, the OS management platform106 can call a routine to apply the install set. This can be, forexample, via a setting in the new OS that is installed.

FIG. 2 is a block diagram of an update platform capable to determine andsend a subset of software components customized for an operating systemto a baseboard management controller of a computing device prior toinstallation of the operating system, according to an example. FIG. 3 isa flowchart of a method for sending a subset of software componentscustomized for an operating system to a baseboard management controllerof a computing device prior to installation of the operating system,according to an example.

The update platform 102 includes, for example, a processing element 210,and a machine-readable storage medium 220 including instructions 222,224, 226 for providing a customized set of software components to acomputing device via a BMC. In some examples, the update platform 102may be implemented, for example, as a virtual machine executing on acomputing device. In some example, the update platform 102 includes thesoftware described to implement the features discussed herein inaddition to hardware used for execution of the software.

Processing element 210 may be, one or multiple central processing unit(CPU), one or multiple semiconductor-based microprocessor, one ormultiple graphics processing unit (GPU), other hardware devices suitablefor retrieval and execution of instructions stored in machine-readablestorage medium 220, or combinations thereof. The processing element 110can be a physical device. Moreover, in one example, the processingelement 210 may include multiple cores on a chip, include multiple coresacross multiple chips, multiple cores across multiple devices (e.g., ifthe computing device 200 includes multiple node devices), orcombinations thereof. Processing element 210 may fetch, decode, andexecute instructions 222, 224, 226 to implement method 300. As analternative or in addition to retrieving and executing instructions,processing element 210 may include at least one integrated circuit (IC),other control logic, other electronic circuits, or combinations thereofthat include a number of electronic components for performing thefunctionality of instructions 222, 224, 226.

Machine-readable storage medium 220 may be any electronic, magnetic,optical, or other physical storage device that contains or storesexecutable instructions. Thus, machine-readable storage medium may be,for example, Random Access Memory (RAM), an Electrically ErasableProgrammable Read-Only Memory (EEPROM), a storage drive, a Compact DiscRead Only Memory (CD-ROM), flash memory, and the like. As such, themachine-readable storage medium can be non-transitory. As described indetail herein, machine-readable storage medium 220 may be encoded with aseries of executable instructions for to select a subset of softwarecomponents for a computing device awaiting an operating system installand sending the subset to the computing device prior to the operatingsystem install.

At 302, the processing element 210 can execute update instructions 222to determine that an OS update is to occur on a computing device. Asnoted above, the update platform can expose an API to an OS managementplatform (e.g., a virtual machine management system). The OS managementplatform can use the API to inform the update platform 102 that an OSinstall is to occur on the computing device by providing informationabout the request. The computing device can be identified along with theOS in the information. In some examples, an address for a BMC of thecomputing device can be mapped to an identifier of the computing device.The update platform 102 may maintain such a mapping (e.g., when a newcomputing device is added to a management network to be supported by theupdate platform, information about that device can be collected).

At 304, the information that is collected can be used by the updateplatform to select a subset of software components for the computingdevice by executing subset instructions 224. A set of the softwarecomponents can be filtered using the OS to be installed on the computingdevice. Further, the software components can be filtered using thehardware present on the computing device. As noted above, the BMC canprovide information about what hardware is present on the computingdevice to the update platform 102. The software components can include,for example, firmware, drivers, etc.

At 306, communications instructions 226 can be executed to send thesubset of software components that were selected for the computingdevice to a BMC of the computing device via a management network. Aninput/output interface 250 (e.g., a network interface card) can be usedfor the transmission. In some examples, the sending can be scheduled.Further, the update platform 102 may have credentials to push the subsetto the storage associated with the BMC. The update platform 102 can sendthe computing device the set prior to the installation of an OS installpackage on the computing device.

FIG. 4 is a block diagram of a computing device with a baseboardmanagement controller capable of storing software components to installcustomized for an operating system prior to installation of thatoperating system. FIG. 5 is a flowchart of a method for receiving acustomized software component subset at a baseboard managementcontroller of a computing device customized for an operating system notyet installed on the computing device.

A processor 430, such as a central processing unit (CPU) or amicroprocessor suitable for retrieval and execution of instructionsand/or electronic circuits can be configured to perform thefunctionality of various higher level modules described herein (e.g.,operating system 416). In certain scenarios, instructions and/or otherinformation, such as operating system information, identifiers, sets andsubsets of information, can be included in memory 432 or other memory.Input/output interfaces 434 may additionally be provided by thecomputing device 400. For example, input devices, such as a keyboard, asensor, a touch interface, a mouse, a microphone, etc, can be utilizedto receive input from an environment surrounding the computing device.Further, an output device, such as a display, can be utilized to presentinformation to users. Examples of output devices include speakers,display devices, amplifiers, etc. Moreover, in certain examples, somecomponents can be utilized to implement functionality of othercomponents described herein. Input/output devices such as communicationdevices like network communication devices or wireless devices can alsobe considered devices capable of using the input/output interfaces 434.In some examples, the BMC 410 can include an input/output interface suchas a NIC.

One or more of the hardware devices included in the computing device 400can include electronic circuitry for implementing the functionalitydescribed herein. In addition or as an alternative, some components maybe implemented as a series of instructions encoded on a machine-readablestorage medium of computing device 400 and executable by processor 430.It should be noted that, in some examples, some modules are implementedas hardware devices, while other modules are implemented as executableinstructions.

In one example, the BMC 410 can run on auxiliary power, thus thecomputing device 400 need not be powered on to an on state where controlof the computing device 400 is handed over to an operating system afterboot. As examples, the BMC 410 may provide so-called “out-of-band”services, such as remote console access, remote reboot and powermanagement functionality, monitoring health of the system, access tosystem logs, and the like. As used herein, a BMC 410 has managementcapabilities for sub-systems of a computing device 400, and is separatefrom a processor or processing element that executes a main operatingsystem of a computing device (e.g., a server or set of servers).

The BMC 410 may comprise an interface, such as a network interface,and/or serial interface that an administrator can use to remotelycommunicate with the BMC 410. As used herein, an “out-of-band” serviceis a service provided by the BMC 410 via a dedicated management channel(e.g., the network interface or serial interface) and is availablewhether the computing device 400 is in powered on state. In someexamples, a BMC 410 may be included as part of an enclosure. In otherexamples, a BMC 410 may be included in one or more of the servers (e.g.,as part of the management subsystem of the server) or connected via aninterface (e.g., a peripheral interface). In some examples, sensorsassociated with the BMC 410 can measure internal physical variables suchas humidity, temperature, power supply voltage, communicationsparameters, fan speeds, operating system functions, or the like. The BMC410 may also be capable to reboot or power cycle the device. As noted,the BMC 410 allows for remote management of the device, as such,notifications can be made to a centralized station such as the updateplatform or a management platform using the BMC 410 and passwords orother user entry can be implemented via the BMC 410.

The BMC 410 can have a storage 414 coupled to the BMC 410. The storage414 can be, for example, on a flash storage incorporated within the BMC410 or accessible via a bus. The storage 414 can act as a localrepository that may also be accessible to an operating system once theoperating system is installed.

The computing device 400 can include hardware components 412. Examplesof hardware components include microcontrollers, controller hubs, asouthbridge, a northbridge, peripheral devices coupled to one or morebus, daughter boards, graphics cards, ASICs, etc. One or more of thehardware devices may be associated with firmware engines. Some of thesefirmware engines can be updated with firmware.

A firmware engine can be implemented using instructions executable by aprocessor and/or logic. In some examples, the firmware engine can beimplemented as platform firmware. Platform firmware may include aninterface such as a basic input/output system (BIOS) or unifiedextensible firmware interface (UEFI) to allow it to be interfaced with.The platform firmware can be located at an address space where theprocessor 430 (e.g., CPU) for the computing device 400 boots. In someexamples, the platform firmware may be responsible for a power onself-test for the computing device 400. In other examples, the platformfirmware can be responsible for the boot process and what, if any,operating system to load onto the computing device 400. Further, theplatform firmware may be capable to initialize various components of thecomputing device 400 such as peripherals, memory devices 432, memorycontroller settings, storage controller settings, bus speeds, video cardinformation, etc. In some examples, platform firmware can also becapable to perform various low level functionality while the computingdevice 400 executes. Moreover, in some examples, platform firmware maybe capable to communicate with a higher level operating system executingon a CPU, for example via an advanced configuration and power interface(ACPI).

In some examples, BMC 410 can take an inventory of the hardwarecomponents 412 present on the computing device 400 as explained indetail above. The inventory can be sent to the update platform. Theupdate platform can be implemented to use the inventory and an operatingsystem install information set to determine a subset of softwarecomponents to send to the computing device as described in method 300.

At 502, the BMC 410 can receive the software component subset from theupdate platform. As noted above, in one example, the update platform canpush the information down to the BMC 410. As used herein, to pushinformation means that the update platform initiates the transaction toprovide the BMC 410 the software component subset (e.g., in response todetermining that the operating system is to be installed on thecomputing device). In some examples, the software component subset isreceived while the computing device is acting as a live server. This canbe accomplished without affecting the live server because the BMC 410 isseparate subsystem from an OS 416 of the live server executing onprocessor 430.

At 504, the BMC 410 can cause the received software component subset tobe stored on a storage 414. The BMC 410 can receive information and thenstore the information in the storage 414 directly or store in a buffermemory and then store the information in the storage 414. As notedabove, the computing device 400 can be configured such that an OS 416with proper configuration (e.g., drivers) can access the storage 414.

At 506, the computing device 400 can receive an operating system updatepackage associated with the operating system install. In one example,the OS update package can be received after the subset. In someexamples, the operating system update package is received via a networkseparate than a management network associated with the BMC. In otherexamples, the OS update package is received via the management network.The OS update package can be stored in a location accessible to aninstruction set executed by the processor 430, for example, a locationthat is capable to boot the OS update package. In another example, theOS update package can be executable by an already running OS 416 on thecomputing device 400, which can facilitate install of the new OS.

At 508, the processor 430 can install the new OS using the OS updatepackage. As noted, the execution can be initiated via an OS currentlyinstalled on the computing device 400 or via a startup routine. Further,in some examples, the update can be scheduled. In one example, while anexisting OS 416 is acting as a live server, an OS management platform106 can schedule a maintenance window where virtual machines and/orprocesses running on the computing device are transferred off of thecomputing device or stopped and additional virtual machines and/orprocesses are not started. Once this is complete, the computing devicecan be brought down for the installation of the new OS.

At 510, the software component subset can be installed. In someexamples, the software components can include drivers. These drivers canbe installed after the new OS is installed. In some examples, becausethere is no need to separately download the subset, the installation ofthe drivers in the subset can occur in the same maintenance window asthe installation of the OS. As noted above, the subset can includedrivers that are identified to work with the OS type. In anotherexample, the BMC 410 can be configured to update or cause update of oneor more firmware engines associated with the hardware components 412that are supported by the received subset.

While certain implementations have been shown and described above,various changes in form and details may be made. For example, somefeatures that have been described in relation to one implementationand/or process can be related to other implementations. In other words,processes, features, components, and/or properties described in relationto one implementation can be useful in other implementations.Furthermore, it should be appreciated that the systems and methodsdescribed herein can include various combinations and/orsub-combinations of the components and/or features of the differentimplementations described. Thus, features described with reference toone or more implementations can be combined with other implementationsdescribed herein.

What is claimed is:
 1. A system comprising: a processor; and anon-transitory storage medium storing instructions executable on theprocessor to: determine that an installation of an operating system isto occur on a computing device coupled to the system over a network;access a repository including a plurality of software components formultiple operating systems and multiple hardware sets; based on thedetermination that the installation of the operating system is to occuron the computing device, query, over the network, a baseboard managementcontroller (BMC) of the computing device for information of a pluralityof hardware devices in the computing device; receive, at the system overthe network from the BMC responsive to the querying, the information ofthe plurality of hardware devices identified by a hardware inventoryperformed by the BMC; filter the plurality of software components in therepository to select a subset of the plurality of software componentsfor the computing device based on an operating system type of theoperating system and the plurality of hardware devices identified by thehardware inventory performed by the BMC; and send, from the system overthe network, the subset of the plurality of software components to theBMC prior to the installation of the operating system using an operatingsystem install package, the sending of the subset of the plurality ofsoftware components to cause an installation by the computing device ofthe operating system from the operating system install package after thesubset of the plurality of software components has arrived at thecomputing device.
 2. The system of claim 1, wherein the instructions areexecutable on the processor to send the subset of the plurality ofsoftware components to the BMC while the computing device is acting as alive server.
 3. The system of claim 1, wherein the sending of the subsetof the plurality of software components is to cause an installation bythe computing device of the subset of the plurality of softwarecomponents retrieved from a storage of the BMC after a completion of theinstallation of the operating system using the operating system installpackage.
 4. The system of claim 1, wherein the instructions areexecutable on the processor to send, from the system, the operatingsystem install package to the computing device after the sending of thesubset of the plurality of software components from the system to theBMC.
 5. The system of claim 1, wherein the installation of the operatingsystem and the installation of the subset of the plurality of softwarecomponents occur in a single maintenance window.
 6. The system of claim1, wherein the operating system type is one of a plurality of differentoperating system types, and wherein different subsets of the pluralityof software components correspond to the different operating systemtypes.
 7. The system of claim 6, wherein the system is to expose anapplication programming interface (API) to an operating systemmanagement platform, and wherein the instructions are executable on theprocessor to: receive information about the installation of theoperating system from the operating system management platform via theAPI; and use the information about the installation of the operatingsystem to select the subset of the plurality of software components. 8.The system of claim 7, wherein the API is to translate requests frommultiple operating system management platforms including the operatingsystem management platform to requests for custom subsets of theplurality of software components including the subset, and wherein theoperating system management platform is a virtual machine managementsystem.
 9. The system of claim 6, wherein the subset of the plurality ofsoftware components includes drivers for the plurality of hardwaredevices, wherein the drivers are specific for the operating system typeof the operating system in the operating system install package.
 10. Amethod comprising: determining, at an update platform comprising ahardware processor, that an installation of an operating system is tooccur on a computing device coupled to the update platform over anetwork, wherein the computing device includes a baseboard managementcontroller (BMC), a storage in the BMC, and a plurality of hardwaredevices, and wherein the update platform includes a repository includinga plurality of software components for multiple operating systems andmultiple hardware sets; based on the determination that the installationof the operating system is to occur on the computing device, querying,by the update platform over the network, the BMC of the computing devicefor information of the plurality of hardware devices in the computingdevice; receiving, at the update platform over the network from the BMCbased on the querying, the information of the plurality of hardwaredevices identified by a hardware inventory performed by the BMC;selecting, by the update platform, a subset of the plurality of softwarecomponents in the repository for the computing device by filtering theplurality of software components based on an operating system type ofthe operating system and the plurality of hardware devices identified bythe hardware inventory of the computing device performed by the BMC; andsending, by the update platform over the network, the subset of theplurality of software components to the storage in the BMC prior to anoperating system install package for the installation of the operatingsystem being present on the computing device, the sending of the subsetof the plurality of software components to cause an installation by thecomputing device of the operating system from the operating systeminstall package after the subset of the plurality of software componentshas arrived at the computing device.
 11. The method of claim 10,comprising: sending, from the update platform, the operating systeminstall package to the computing device after the update platform sendsthe subset of the plurality of software components to the storage in theBMC.
 12. The method of claim 10, further comprising: receiving, by thecomputing device, the operating system install package after the subsetof the plurality of software components has arrived at the computingdevice.
 13. The method of claim 12, wherein the BMC is separate from aprocessor of the computing device, the method further comprising:executing, by the processor, the operating system installed from theoperating system install package.
 14. The method of claim 13, furthercomprising: accessing, by the operating system executed on theprocessor, the storage in the BMC to retrieve the subset of theplurality of software components; and installing, by the computingdevice, the subset of the plurality of software components on thecomputing device after retrieval of the subset of the plurality ofsoftware components from the storage in the BMC.
 15. The method of claim13, wherein the BMC is run on auxiliary power and is able performoperations of the BMC while the computing device is powered off.
 16. Themethod of claim 10, wherein the operating system type is one of aplurality of different operating system types, and wherein differentsubsets of the plurality of software components correspond to thedifferent operating system types.
 17. The method of claim 10,comprising: exposing, by the update platform, an application programminginterface (API) to a virtual machine management system; receiving, atthe update platform, information about the installation of the operatingsystem from the virtual machine management system via the API; andusing, by the update platform, the information about the installation ofthe operating system to select the subset of the plurality of softwarecomponents.
 18. A non-transitory machine-readable storage medium storinginstructions that upon execution cause a system to: determine that aninstallation of an operating system is to occur on a computing devicecoupled to the system over a network, wherein the computing deviceincludes a baseboard management controller (BMC), a storage in the BMC,and a plurality of hardware devices; access a repository including aplurality of software components for multiple operating systems andmultiple hardware sets; based on the determination that the installationof the operating system is to occur on the computing device, query, overthe network, the BMC of the computing device for information of theplurality of hardware devices in the computing device; receive, at thesystem over the network from the BMC responsive to the querying, theinformation of the plurality of hardware devices identified by ahardware inventory performed by the BMC; filter the plurality ofsoftware components in the repository to select a subset of theplurality of software components for the computing device based on anoperating system type of the operating system and the plurality ofhardware devices identified by the hardware inventory performed by theBMC of the computing device; and send, from the system over the network,the subset of the plurality of software components to the storage in theBMC prior to the installation of the operating system using an operatingsystem install package, the sending of the subset of the plurality ofsoftware components to cause an installation by the computing device ofthe operating system from the operating system install package after thesubset of the plurality of software components has arrived at thecomputing device.
 19. The non-transitory machine-readable storage mediumof claim 18, wherein the plurality of software components comprisedrivers.
 20. The non-transitory machine-readable storage medium of claim18, wherein the instructions upon execution cause the system to: exposean application programming interface (API) to a virtual machinemanagement system receive, at the system, information about theinstallation of the operating system from the virtual machine managementsystem via the API; and use the information about the installation ofthe operating system to select the subset of the plurality of softwarecomponents.